System acquisition mechanism for fixed devices in mobile broadband networks

ABSTRACT

Briefly, in accordance with one or more embodiments, a fixed device synchronizes with a downlink channel of a network, acquires a master information block including a last system update time; and executes cell selection without acquiring other system information if the last system update time is before the last system access time. Furthermore, the fixed device may listen only for system information block messages that it needs, and ignore other system information blocks. A bitmap may indicate which system information block messages should be listed to for fixed devices, and which may be ignored. In some embodiments, one or more system information blocks may be designated for fixed devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.15/223,357 filed on Jul. 29, 2016, which in turn is a continuation ofU.S. application Ser. No. 13/995,163 filed on Sep. 18, 2013, which isthe National Stage Application of International Application No.PCT/US2011/062824 filed on Dec. 1, 2011, which in turn claims thebenefit of U.S. Provisional Application No. 61/471,042 filed Apr. 1,2011. Said application Ser. Nos. 15/223,357, 13/995,163,PCT/US2011/062824, and 61/471,042 are hereby incorporated herein byreference in their entireties.

BACKGROUND

In a wireless mobile broadband system such as a Third GenerationPartnership Project (3GPP) Long Term Evolution (LTE) network, a userequipment (UE) device performs a network acquisition process in order toget connected to the network. The network acquisition process comprisesthe following steps: UE power up; downlink synchronization anddetermination of the physical cell identifier (ID); Master InformationBlock (MIB) acquisition; shared channel resource acquisition; controlinformation acquisition; retrieval of System Information Blocks (SIBs);cell selection; and initial access by the UE on the network. However,since a fixed UE generally does not move, it would be beneficial for afixed UE to skip any of the network acquisition steps that are gearedtoward mobile devices and which may not be required by a fixed UE inorder to speed up initial network entry by a fixed UE.

DESCRIPTION OF THE DRAWING FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, suchsubject matter may be understood by reference to the following detaileddescription when read with the accompanying drawings in which:

FIG. 1 is a block diagram of an example machine-to-machine (M2M) systemwhich may utilize enhanced system acquisition for fixed devices inaccordance with one or more embodiments;

FIG. 2 is a block diagram of an example machine-to-machine (M2M) systemas shown in FIG. 1 wherein the system may include a Long Term Evolution(LTE) network or the like for broadband access in accordance with one ormore embodiments;

FIG. 3 is a flow diagram of a method of network access for a fixeddevice based on modified master information block acquisition inaccordance with one or more embodiments;

FIG. 4 is a flow diagram of a method of network access for a fixeddevice based on acquisition of a fixed device system information blockin accordance with one or more embodiments;

FIG. 5 is a flow diagram of a method of network access for a fixeddevice based on listening to a bitmap to determine any change to thenetwork access information in accordance with one or more embodiments;

FIG. 6 is a diagram of the transmission of system information blocks fora mobile device versus a fixed device in accordance with one or moreembodiments;

FIG. 7 is a block diagram of an information handling system capable ofimplementing enhanced network acquisition for a fixed device in a mobilebroadband network in accordance with one or more embodiments; and

FIG. 8 is an isometric view of an information handling system of FIG. 7that optionally may include a touch screen in accordance with one ormore embodiments.

It will be appreciated that for simplicity and/or clarity ofillustration, elements illustrated in the figures have not necessarilybeen drawn to scale. For example, the dimensions of some of the elementsmay be exaggerated relative to other elements for clarity. Further, ifconsidered appropriate, reference numerals have been repeated among thefigures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components and/or circuitshave not been described in detail.

In the following description and/or claims, the terms coupled and/orconnected, along with their derivatives, may be used. In particularembodiments, connected may be used to indicate that two or more elementsare in direct physical and/or electrical contact with each other.Coupled may mean that two or more elements are in direct physical and/orelectrical contact. However, coupled may also mean that two or moreelements may not be in direct contact with each other, but yet may stillcooperate and/or interact with each other. For example, “coupled” maymean that two or more elements do not contact each other but areindirectly joined together via another element or intermediate elements.Finally, the terms “on,” “overlying,” and “over” may be used in thefollowing description and claims. “On,” “overlying,” and “over” may beused to indicate that two or more elements are in direct physicalcontact with each other. However, “over” may also mean that two or moreelements are not in direct contact with each other. For example, “over”may mean that one element is above another element but not contact eachother and may have another element or elements in between the twoelements. Furthermore, the term “and/or” may mean “and”, it may mean“or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some,but not all”, it may mean “neither”, and/or it may mean “both”, althoughthe scope of claimed subject matter is not limited in this respect. Inthe following description and/or claims, the terms “comprise” and“include,” along with their derivatives, may be used and are intended assynonyms for each other.

Referring now to FIG. 1, a block diagram of an examplemachine-to-machine (M2M) system which may utilize enhanced systemacquisition for fixed devices in accordance with one or more embodimentswill be discussed. As shown in FIG. 1, a machine-to-machine (M2M) system100 may comprise a base transceiver station (BTS) 110 coupled to anetwork 114 via backhaul 112. The base transceiver station 110 mayprovide an air interface 124 between one or more mobile devices such asmobile device 116 and/or one or more fixed devices such as a first fixeddevice 118, a second fixed device 120, up to an Nth fixed device 122.The base transceiver station 110 may be deployed in a cell of a mobilebroadband network such as a Long Term Evolution (LTE) network asdiscussed herein. The fixed devices and/or the mobile devices and thebase transceiver station 110 together comprise an air interface 124, andbackhaul 112 and network 114 comprise a core network 130. In someembodiments as will be discussed in further detail with respect to FIG.2 below, M2M system 100 may comprise a mobile broadband network inaccordance with a Long Term Evolution (LTE) standard wherein basetransceiver station 110 comprises an enhanced Node B (eNB) and themobile devices and fixed devices comprise user equipment (UE).Furthermore, in some embodiments network 114 may comprise the Internet.In one or more alternative embodiments, M2M system 100 may comprise anyvarious type of broadband network such as Worldwide Interoperability forMicrowave Access (WiMAX) network in accordance with an Institute forElectrical and Electronics Engineers (IEEE) standard such as an IEEE802.16e standard, or a WiMAX-II network in accordance with an IEEE802.16m standard. Furthermore, M2M system 100 may be compliant with anIEEE 802.16p standard. However, these are merely example implementationsfor M2M system 100, and the scope of the claimed subject matter is notlimited in these respects.

In one or more embodiments, fixed devices such as fixed device 118,fixed device 120 or fixed device 122 may utilize random access tocommunicate via M2M network. In such embodiments, M2M system 100 allowsfor the devices to communicate data they may have to transmit over thecore network 130 to a remote device or server coupled to network 114when such data is available. For example, field data may be gathered bythe devices and sent back to a monitoring station for collection andanalysis. In such an example, the fixed devices such as fixed device118, fixed device 120, and fixed device 122 may comprise parking meters.When the parking meter is full of coins and is ready to be emptied, agiven parking meter may communicate its state to a monitoring servercoupled to network 114, in which case an operator may then go thatparking meter and remove the coins stored therein. The parking meter maythen continue to operate until it is again full and sends a subsequentsignal to the monitoring server. As another example, the fixed devicesmay comprise vending machines such as a drink vending machine. A givenmachine may communicate to a remote server that a given drink is low toindicate that an operator should come to that machine and refill the lowdrink. In yet another example, fixed devices may be deployed to monitorfor the presence of a specified hazardous substance such as a chemicalagent, a biological agent, and/or a radionuclide wherein the fixeddevice 118 includes an appropriate sensor. In the event the fixed device118 detects the presence of the target substance, the fixed device maycommunicate to a remote server of the result and/or that an appropriateresponse should be taken. Various other types of fixed devices may bedeployed in M2M system 100, and the scope of the claimed subject matteris not limited in these respects. In one or more embodiments, M2M system100 may comprise a mobile broadband network such as an LTE network asshown in and described with respect to FIG. 2, below.

Referring now to FIG. 2, a block diagram of an examplemachine-to-machine (M2M) system of FIG. 1 wherein the system may includea Long Term Evolution (LTE) network or the like for broadband access inaccordance with one or more embodiments will be discussed. FIG. 2 showsa block diagram of the overall architecture of machine-to-machine (M2M)system 100 comprising a Third Generation Partnership Project (3GPP) LongTerm Evolution (LTE) network that includes network elements andstandardized interfaces. At a high level, M2M system 100 comprises acore network (CN) 130, also referred to as an evolved Packet System(EPC), and an air-interface access network 124, also referred to as anevolved Universal Terrestrial Radio Access Network (E-UTRAN). Corenetwork 130 is responsible for the overall control of the various UserEquipment (UE), such as fixed device 118, connected to the M2M system100 and for the establishment of the bearers. Air interface network 124is responsible for radio-related functions in communication with basetransceiver station 110, also referred to as an enhanced Node B (eNB).

The main logical nodes of core network 130 provide a backhaul 112include a Serving General Packet Radio Service (GPRS) Support Node(SGSN) 212, Mobility Management Entity (MME) 214, a Home SubscriberServer (HSS) 216, a Serving Gateway (SGW) 210, a Packet Data Network(PDN) Gateway (PDN GW) 222, and a Policy and Charging Rules Function(PCRF) Manager 224. Serving Gateway 210 couples to Universal TerrestrialRadio Access Network (UTRAN) 218 to couple base transceiver station 110as eNB to one or more other eNBs. Mobility Management Entity 214 couplesto Global System for Mobile Communications (GSM) Enhanced Data rates forGSM Evolution (EDGE) Radio Access Network (GERAN) 220 to couple basetransceiver station 110 and base station controller as A interfaces toone or more other base transceiver stations. The network elements ofcore network 130 are interconnected by standardized interfaces toprovide various network functions, and the scope of the claimed subjectmatter is not limited in these respects.

While core network 130 includes many logical nodes, air interfacenetwork 124 comprises base transceiver station 110 as an evolved Node B(eNB) that connects to one or more User Equipment (UE) such as fixeddevice 118. Although FIG. 2 shows on user equipment, multiple fixeddevices and/or mobile devices may coupe with base transceiver station110, and the scope of the claimed subject matter is not limited in thisrespect. For normal user traffic, as opposed to broadcast traffic, thereis no centralized controller air interface, and as such the architectureof air interface 124 is referred to as flat. Multiple eNBs may beinterconnected via an interface referred to as “X2” and to the evolvedpacket core network 130 by an S1 interface, more specifically to MME 214by an S1-MME interface and to the SGW 210 by an S1-U interface. Theprotocols that run between the eNBs and the UEs are generally referredto as action script (AS) protocols.

In one or more embodiments, the baste transceiver station 110 as an eNBhosts the physical (PHY), Medium Access Control (MAC), Radio LinkControl (RLC), and Packet Data Control Protocol (PDCP) layers, and whichinclude the functionality of user-plane header-compression andencryption. Base transceiver station 110 also provides Radio ResourceControl (RRC) functionality corresponding to the control plane, andperforms many functions including radio resource management, admissioncontrol, scheduling, enforcement of negotiated uplink (UL) quality ofservice (QoS), cell information broadcast, ciphering/deciphering of userand control plane data, and compression/decompression of downlink/uplink(DL/UL) user plane packet headers.

The RRC layer in base transceiver station 110 covers functions relatedto the radio bearers, such as radio bearer control, radio admissioncontrol, radio mobility control, scheduling and dynamic allocation ofresources to UEs in both uplink and downlink, source rate and PITadaptation, header compression for efficient use of the radio interface,security of all data sent over the radio interface, and connectivity tothe evolved packet core network 130. The RRC layer makes handoverdecisions based on neighbor cell measurements sent by the UEs, generatespages for the UEs over the air, broadcasts system information, controlsUE measurement reporting, such as the periodicity of Channel QualityInformation (CQI) reports, and allocates cell-level temporaryidentifiers to active UEs. The RRC layer also executes transfer of UEcontext from a source eNB to a target eNB during handover, and providesintegrity protection for RRC messages. Additionally, the RRC layer isresponsible for the setting up and maintenance of radio bearers. Inaddition, PCRF 224 and PDN GW couple to Internet protocol (IP) services226 and network 114 which may comprise the Internet. Thus, FIG. 2 showsan embodiment of M2M system 100 as a 3GPP LTE network as one of severalexample broadband networks, and the scope of the claimed subject matteris not limited in this respect. An example method of network access fora fixed device is shown in and described with respect to FIG. 3, below.

Referring now to FIG. 3, a flow diagram of a method of network accessfor a fixed device based on modified master information blockacquisition in accordance with one or more embodiments will bediscussed. Method 300 illustrates one particular embodiment of a methodof network access for a fixed device based on modified masterinformation block acquisition in a mobile broad band network. However,in one or more alternative embodiments, various other orders of theblocks of method 300 may be implemented, with more or fewer blocks, andthe scope of the claimed subject matter is not limited in this respect.As shown in FIG. 3, method 300 comprises a method by which a fixeddevice 118 user equipment (UE) may implement to perform network accessto connect to M2M system 100 of FIG. 1. Method 300 for a fixed device118 UE is substantially similar to a method by which mobile devices mayperform network access with the following modifications. At block 310,the UE may power up and then may perform downlink synchronization atblock 312. The UE may then perform master information block (MIB)acquisition at block 314. In one or more embodiments, the basetransceiver station 110 or enhanced Node B (eNB) may include an optionalfield transmitted in the MIB that indicated to the UE the time and/ordate information when the information for M2M system 100 was lastupdated. For example, the MIB field may comprise an 8-digit field called“Last System Update Time” wherein four digits may indicate the year, twodigits may indicate the month, and two digits may indicate the day. Whenthe fixed device 118 UE receives this MIB field from the eNB, adetermination may be made at decision block 316 whether the last updatetime as indicated in the MIB field occurred before the last time thatthe fixed device 118 UE accessed the system. If the last system updatetime occurred before the last access, then the UE already has the mostup to date system information, and the UE may proceed directly to cellselection at block 324. Otherwise, if the last system update timeoccurred after the last time that the UE accessed the system, then theUE needs to obtain the updated system information by acquiring controlinformation at block 318, acquiring shared channel resource informationat block 320, and retrieving system information blocks at block 322.After obtaining the updated system information, the UE may then performcell selection at block 324. After cell selection, the UE may thenaccess the network. In general, method 300 allows for fixed devices toobtain updated system information for M2M system 100 if the systeminformation has not been updated since the last access time by the UE.The UE may store the date of its last successful access and also a copyof the system information obtained by the UE during its last successfulaccess. The UE may use the date of the last successful access to compareto the MIB field information regarding the date/time of the last time atwhich the system information was update for executing decision block316. If there has been no update to the system information, the UE mayjust use its stored system information from the last access to accessthe network. Method thus uses a modified master information block (MIB)to implement enhanced system access for fixed devices. A method ofnetwork access for a fixed device based on a system information block(SIB) is shown in and described with respect to FIG. 4, below.

Referring now to FIG. 4, a flow diagram of a method of network accessfor a fixed device based on acquisition of a fixed device systeminformation block in accordance with one or more embodiments will bediscussed. Method 400 illustrates one particular embodiment of a methodof network access based on acquisition of a fixed device systeminformation block in a mobile broad band network. However, in one ormore alternative embodiments, various other orders of the blocks ofmethod 400 may be implemented, with more or fewer blocks, and the scopeof the claimed subject matter is not limited in this respect. As shownin FIG. 4, method 400 comprises a method by which a fixed device 118user equipment (UE) may implement to perform network access to connectto M2M system 100 of FIG. 1. Method 400 for a fixed device 118 UE issubstantially similar to a method by which mobile devices may performnetwork access with the following modifications. The fixed device 118 UEmay power up at block 410, and may perform downlink synchronization atblock 412. The UE may then acquire a master information block (MIB) atblock 414, and may acquire control information at block 418. The UE thenacquires shared channel resource information at block 420, and retrievesone or more fixed device system information block (SIB) messages atblock 422. Cell selection may then be performed at block 424. After cellselection, the UE may determine the future time or times at which one ormore future SIB messages may be broadcast by the eNB for the cell withwhich the UE is communicating. For a Long Term Evolution (LTE) typenetwork, the eNB may transmit multiple system information block (SIB)messages. In one or more embodiments, one or more of the SIB messagesmay be defined as a separate SIB message intended for fixedmachine-to-machine (M2M) devices. The fixed device 118 UE will monitorfor broadcasts of the fixed device SIB messages and may ignore the otherSIB messages that are intended for mobile devices. The fixed SIBmessages may be broadcast at a specified time or times that the UE maydetermine from the eNB. After determining the broadcast time or timesfor future fixed device SIB messages, the fixed device 118 UE may enterinto a sleep or idle mode at block 428. The UE may determine at block420 when the next fixed SIB message broadcast time occurs, and mayremain in a sleep or idle mode at block 428 until the time of the fixeddevice SIB message broadcast. When fixed device SIB messages arebroadcast, the fixed device 118 UE may wake up and receive the fixeddevice SIB messages broadcast by the eNB. It should be noted that thetime or times at which the fixed device 118 UE wakes up and receives thefixed device SIB messages may be the same time as or may be a differenttime from the time or times at which the fixed device 118 UE wakes upand transmits its data, and the scope of the claimed subject matter isnot limited in this respect. By waking up to receive only the fixeddevice SIB messages while remaining in a sleep or idle mode when mobiledevice SIB messages are broadcast, fixed devices may conserve batterpower as one example, although the scope of the claimed subject matteris not limited in this respect. An example method by which a fixeddevice may receive a bitmap to determine any change to the networkaccess information is shown in and described with respect to FIG. 5,below.

Referring now to FIG. 5, a flow diagram of a method of network accessfor a fixed device based on listening to a bitmap to determine anychange to the network access information in accordance with one or moreembodiments will be discussed. Method 500 illustrates one particularembodiment of a method of network access for a fixed device based onlistening to a bitmap to determine any change to the network accessinformation in a mobile broad band network. However, in one or morealternative embodiments, various other orders of the blocks of method500 may be implemented, with more or fewer blocks, and the scope of theclaimed subject matter is not limited in this respect. As shown in FIG.5, method 500 comprises a method by which a fixed device 118 userequipment (UE) may implement to perform network access to connect to M2Msystem 100 of FIG. 1. Method 500 for a fixed device 118 UE issubstantially similar to a method by which mobile devices may performnetwork access with the following modifications. The fixed device 118 UEmay power up at block 510, and may perform downlink synchronization atblock 512. The UE may then acquire master information block informationat block 514, and may acquire control information at block 516. The UEacquires shared channel resource information at block 518. The UE maythen listen at block 520 for a special bitmap broadcast at the commonbroadcast channel by the base transceiver station 110 or enhanced Node B(eNB). The fixed device 118 UE may listen for the broadcast bitmapinstead of listening for every system information block (SIB) messagethat may be intended for mobile devices. Such a bitmap may be arrangedso as to indicate whether there has been any change or no change to thesystem information in the last second, minute, hour, day, week, year,and so on. For example, the bitmap may be as follows:

second bit 0 minute bit 0 day bit 0 week bit 1 month bit 0Thus, a 5-bit bit map may be broad cast at the common broadcast channelto indicate to the fixed devices when the last system update occurred.In the above example, the bitmap indicates that the system informationwas updated at least one week ago but less than one month ago. Othertypes of bitmaps may be utilized as well, with a fewer or greater numberof bits, and the scope of the claimed subject matter is not limited inthis respect. After receiving the bitmap broadcast by the eNB, the fixeddevice 118 UE compares at block 522 the received bitmap with a storedcopy of a previous bitmap or timestamp for the last known time that thesystem information was updated. The fixed device 118 UE may store alocal copy of a previously received bitmap and/or a timestamp of thelast system update time. If there has been no change in the systeminformation as determined at block 522, then the fixed device 118 UE mayproceed directly to cell selection at block 526. Otherwise, if thesystem information has been updated, then the fixed device 118 UEretrieves one or more updated system information block messages at block525 and then performs cell selection at block 526. In such anarrangement, the fixed device 118 UE does not need to listen to all ofthe SIB messages unless and until the system information is updated. Ifthere has been no update, then the UE does not need to listen to the SIBmessages. Furthermore, the bitmap broadcast by the eNB may trackrelative rather than absolute time so that the size of the bitmap may bereduced with respect to absolute time data, and therefore also mayrequire less processing power as well. In some embodiments, when thefixed device 118 UE does retrieve updated system information blockmessages at block 524, the fixed device 1118 also may just retrieve SIBmessages that are designated for fixed devices as shown in and describedwith respect to FIG. 6, below.

Referring now to FIG. 6, a diagram of the transmission of systeminformation blocks for a mobile device versus a fixed device inaccordance with one or more embodiments will be discussed. As shown inFIG. 6, an arrangement 610 or scheme for broadcasting system informationblock (SIB) messages for mobile devices is shown in comparison with anarrangement 612 or scheme for broadcasting system information block(SIB) messages for fixed devices. As shown in arrangement 610, SIBmessages are sent from a base transceiver station 110 (eNB) at 616 toone or more mobile device 116 (UE) at 614. Mobile broadband networkssuch as Long Term Evolution (LTE) compliant systems support thetransmission of multiple SIB messages, for example SIB1, SIB2, SIB3,SIB4, SIB5, and so on, as shown in arrangement 610. For fixedmachine-to-machine (M2M) devices, listening to all of the multiple SIBmessages for mobile devices is not required. As a result, in one or moreembodiments, in the arrangement 612 for fixed devices, the basetransceiver station 110 (eNB) at 620 may transmit a bitmap (BITMAP) tothe fixed devices (UE) at 618 wherein the bitmap indicates which of theSIB messages the fixed devices need to listen to, and which SIB messagesthe fixed devices may safely ignore. For example, if there are eightunique SIB messages, an 8-bit bitmap may indicate which ones of theeight SIB messages the fixed devices may listen to. In some embodiments,the bitmap (BITMAP) may indicate which of the SIB messages have changedor not changed, and the fixed device 118 (UE) knows from the bitmap tolisten for the changed SIB messages to that the fixed device 118 (UE)may update its own saved system information accordingly. Furthermore,the base transceiver station 110 (eNB) may transmit a special systeminformation block (SIBX) message that is intended for fixed devices. Forexample, the special SIBX message for fixed devices may be the same orsimilar to the fixed device SIB message as descried with respect to FIG.4, above. The bitmap (BITMAP) may indicate which one of the SIB messagesis the SIBX message for fixed devices. Likewise, the bitmap (BITMAP) mayindicate whether there has been any change to the SIBX message so thatthe fixed device 118 (UE) may ignore the SIBX message if it has not beenupdated and the fixed device (UE) has previously stored the SIBX messageinformation, or to otherwise listen to the SIBX message when the bitmap(BITMAP) indicates that the SIBX message has been changed and needs tobe updated at the fixed device 118 (UE). It should be known that theparticular arrangement of the transmission of system information blocksfor a mobile device versus a fixed device as shown in FIG. 6 is merelyexample of several possible arrangements, and the scope of the claimedsubject matter is not limited in this respect.

Referring now to FIG. 7, a block diagram of an information handlingsystem capable of implementing an enhanced system acquisition mechanismfor a fixed device in a mobile broadband network in accordance with oneor more embodiments will be discussed. Information handling system 700of FIG. 7 may tangibly embody one or more of any of the network elementsor devices of the machine-to-machine system 100 as shown in anddescribed with respect to FIG. 1. For example, information handlingsystem 700 may represent the hardware of fixed device 118, mobile device116 and/or base transceiver station 110, with greater or fewercomponents depending on the hardware specifications of the particulardevice or network element. Although information handling system 700represents one example of several types of computing platforms,information handling system 700 may include more or fewer elementsand/or different arrangements of elements than shown in FIG. 7, and thescope of the claimed subject matter is not limited in these respects.

In one or more embodiments, information handling system 700 may includean applications processor 710 and a baseband processor. Applicationsprocessor 710 may be utilized as a general purpose processor to runapplications and the various subsystems for information handling system700. Applications processor 710 may include a single core oralternatively may include multiple processing cores wherein one or moreof the cores may comprise a digital signal processor or digital signalprocessing core. Furthermore, applications processor 710 may include agraphics processor or coprocessor disposed on the same chip, oralternatively a graphics processor coupled to applications processor 710may comprise a separate, discrete graphics chip. Applications processor710 may include on board memory such as cache memory, and further may becoupled to external memory devices such as synchronous dynamic randomaccess memory (SDRAM) 714 for storing and/or executing applicationsduring operation, and NAND flash 716 for storing applications and/ordata even when information handling system 700 is powered off. Basebandprocessor 712 may control the broadband radio functions for informationhandling system 700. Broadband processor 712 may store code forcontrolling such broadband radio functions in a NOR flash 718. Basebandprocessor 712 controls a wireless wide area network (WWAN) transceiver722 which is used for modulating and/or demodulating broadband networksignals, for example for communicating via a 3GPP LTE network or thelike as discussed herein with respect to FIG. 2. The WWAN transceiver720 couples to one or more power amps 722 respectively coupled to one ormore antennas 724 for sending and receiving radio-frequency signals viathe WWAN broadband network. The baseband processor 712 also may controla wireless local area network (WLAN) transceiver 726 coupled to one ormore suitable antennas 728 and which may be capable of communicating viaa Wi-Fi, Bluetooth, and/or an amplitude modulation (AM) or frequencymodulation (FM) radio standard including an IEEE 802.11 a/b/g/n standardor the like. It should be noted that these are merely exampleimplementations for applications processor 710 and baseband processor712, and the scope of the claimed subject matter is not limited in theserespects. For example, any one or more of SDRAM 714, NAND flash 716and/or NOR flash 718 may comprise other types of memory technology suchas magnetic memory, chalcogenide memory, phase change memory, or ovonicmemory, and the scope of the claimed subject matter is not limited inthis respect.

In one or more embodiments, applications processor 710 may drive adisplay 730 for displaying various information or data, and may furtherreceive touch input from a user via a touch screen 732 for example via afinger or a stylus. An ambient light sensor 734 may be utilized todetect an amount of ambient light in which information handling system700 is operating, for example to control a brightness or contrast valuefor display 730 as a function of the intensity of ambient light detectedby ambient light sensor 734. One or more cameras 736 may be utilized tocapture images that are processed by applications processor 710 and/orat least temporarily stored in NAND flash 716. Furthermore, applicationsprocessor may couple to a gyroscope 738, accelerometer 740, magnetometer742, audio coder/decoder (CODEC) 744, and/or global positioning system(GPS) controller 746 coupled to an appropriate GPS antenna 748, fordetection of various environmental properties including location,movement, and/or orientation of information handling system 700. AudioCODEC 744 may be coupled to one or more audio ports 750 to providemicrophone input and speaker outputs either via internal devices and/orvia external devices coupled to information handling system via theaudio ports 750, for example via a headphone and microphone jack. Inaddition, applications processor 710 may couple to one or moreinput/output (I/O) transceivers 752 to couple to one or more I/O ports754 such as a universal serial bus (USB) port, a high-definitionmultimedia interface (HDMI) port, a serial port, and so on. Furthermore,one or more of the I/O transceivers 752 may couple to one or more memoryslots 756 for optional removable memory such as secure digital (SD) cardor a subscriber identity module (SIM) card, although the scope of theclaimed subject matter is not limited in these respects.

FIG. 8 is an isometric view of an information handling system of FIG. 7that optionally may include a touch screen in accordance with one ormore embodiments. FIG. 8 shows an example implementation of informationhandling system 700 of FIG. 7 tangibly embodied as a cellular telephone,smartphone, or tablet type device or the like. In one or moreembodiments, the information handling system 700 may comprise fixeddevice 118 or mobile device 116 of FIG. 1, although the scope of theclaimed subject matter is not limited in this respect. The informationhandling system 700 may comprise a housing 810 having a display 730which may include a touch screen 732 for receiving tactile input controland commands via a finger 816 of a user and/or a via stylus 818 tocontrol one or more applications processors 710. The housing 810 mayhouse one or more components of information handling system 700, forexample one or more applications processors 710, one or more of SDRAM714, NAND flash 716, NOR flash 718, baseband processor 712, and/or WWANtransceiver 720. The information handling system 700 further mayoptionally include a physical actuator area 820 which may comprise akeyboard or buttons for controlling information handling system via oneor more buttons or switches. The information handling system 700 mayalso include a memory port or slot 756 for receiving non-volatile memorysuch as flash memory, for example in the form of a secure digital (SD)card or a subscriber identity module (SIM) card. Optionally, theinformation handling system 700 may further include one or more speakersand/or microphones 824 and a connection port 754 for connecting theinformation handling system 700 to another electronic device, dock,display, battery charger, and so on. In addition, information handlingsystem 700 may include a headphone or speaker jack 828 and one or morecameras 736 on one or more sides of the housing 810. It should be notedthat the information handling system 700 of FIG. 8 may include more orfewer elements than shown, in various arrangements, and the scope of theclaimed subject matter is not limited in this respect.

Although the claimed subject matter has been described with a certaindegree of particularity, it should be recognized that elements thereofmay be altered by persons skilled in the art without departing from thespirit and/or scope of claimed subject matter. It is believed that thesubject matter pertaining to system acquisition mechanisms for fixeddevices in mobile broadband networks and/or many of its attendantutilities will be understood by the forgoing description, and it will beapparent that various changes may be made in the form, constructionand/or arrangement of the components thereof without departing from thescope and/or spirit of the claimed subject matter or without sacrificingall of its material advantages, the form herein before described beingmerely an explanatory embodiment thereof, and/or further withoutproviding substantial change thereto. It is the intention of the claimsto encompass and/or include such changes.

1. (canceled)
 2. An apparatus of a bandwidth reduced low complexity (BL)UE, comprising: a memory to store system information for a network; andone or more baseband processors to: decode information from a bandwidthreduced (BR) system information block (SIB) that includes a value tag;read the value tag with the system information to verify whether thesystem information is still valid; and if the system information is nolonger valid, acquire new system information from the network, andupdate the system information in the memory with the new systeminformation.
 3. The apparatus of claim 2, wherein the one or morebaseband processors are to continue using the system information storedin the memory until the new system information is acquired.
 4. Theapparatus of claim 2, wherein the one or more baseband processors are toperform network acquisition using the new system information.
 5. Theapparatus of claim 2, wherein the BR SIB comprises a specific SIB formachine-to-machine (M2M) SIBs.
 6. The apparatus of claim 2, wherein theone or more baseband processors are configured to receive the BR SIB viaa shared channel or via a broadcast channel.
 7. The apparatus of claim2, wherein the BR SIB is scheduled to occur separate from systeminformation block-1 (SIB-1).
 8. An apparatus of an evolved NodeB (eNB)to communicate with a bandwidth reduced low complexity (BL) UE, the eNBcomprising: a memory to store information for a network; one or morebaseband processors to encode a bandwidth reduced (BR) systeminformation block (SIB) for the BL UE wherein the BR SIB includes avalue tag that indicates to the BL UE whether system information for thenetwork is still valid; and if the system information is no longervalid, to encode new system information to be acquired by the BL UE. 9.The apparatus of claim 8, wherein the one or more baseband processorsare to continue to communicate with the BL UE using the systeminformation stored in the memory until the new system information isacquired by the UE.
 10. The apparatus of claim 8, wherein the one ormore baseband processors are to engage in network acquisition with theBL UE using the new system information.
 11. The apparatus of claim 8,wherein the BR SIB comprises a specific SIB for machine-to-machine (M2M)SIBs.
 12. The apparatus of claim 8, wherein the one or more processorsare configured to send the BR SIB to the UE via a shared channel or viaa broadcast channel.
 13. The apparatus of claim 8, wherein the one ormore baseband processors are to schedule the BR SIB to occur separatefrom system information block-1 (SIB-1).
 14. One or more non-transitorystorage media that, when executed by an apparatus of a bandwidth reducedlow complexity (BL) UE, result in: decoding information from a bandwidthreduced (BR) system information block (SIB) received from a networkwherein the BR SIB includes a value tag; reading the value tag with thesystem information to verify whether system information for the networkis still valid; and if the system information is no longer valid,acquiring new system information from the network, and updating thesystem information with the new system information.
 15. The one or morenon-transitory storage media of claim 14, wherein the instructions, whenexecuted, further result in continuing to use previous information untilthe new system information is acquired.
 16. The one or morenon-transitory storage media of claim 14, wherein the instructions, whenexecuted, further result in performing network acquisition using the newsystem information.
 17. The one or more non-transitory storage media ofclaim 14, wherein the BR SIB comprises a specific SIB formachine-to-machine (M2M) SIBs.
 18. The one or more non-transitorystorage media of claim 14, wherein the instructions, when executed,further result in receiving the BR SIB via a shared channel or via abroadcast channel.
 19. The one or more non-transitory storage media ofclaim 14, wherein the BR SIB is scheduled to occur separate from systeminformation block-1 (SIB-1).